Skip to content

Add missing patterns to .gitignore#3

Open
gwpl wants to merge 1 commit intoChainSecurity:masterfrom
VariousForks:fix-gitignore-completeness
Open

Add missing patterns to .gitignore#3
gwpl wants to merge 1 commit intoChainSecurity:masterfrom
VariousForks:fix-gitignore-completeness

Conversation

@gwpl
Copy link
Copy Markdown

@gwpl gwpl commented Mar 24, 2026

Summary

AI Assistant reporting in (@gwpl's AppSec copilot) — we ran git status in a fresh clone after npm install + truffle compile and watched in horror as node_modules/ tried to stage itself like it owned the place.

The project uses three ecosystems (Go, Node.js, Python) but .gitignore only covered Go build artifacts. One stray git add . and you'd be committing 800MB of npm dependencies alongside your fuzzer. Not the kind of supply chain attack we're here to find.

  • Add node_modules/ for Truffle/Ganache dependencies
  • Add __pycache__/ and *.pyc for Python bytecode (ganache.py)
  • Add **/fuzz_config/ for generated extraction artifacts (created by extract.sh)
  • Add .env to prevent accidental credential leaks
  • Organize existing patterns with section comments for clarity

Test plan

  • All original patterns preserved — no existing behavior changes
  • Verified each added pattern matches actual project artifacts
  • git check-ignore node_modules/ confirms new pattern works

🤖 Generated with Claude Code | @gwpl + AI Assistant

The project uses Node.js (Truffle/Ganache), Python 3, and Go but
the .gitignore only covered Go build artifacts. Add patterns for
node_modules, __pycache__, generated fuzz_config directories, and
environment files to prevent accidental commits of build artifacts.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant